Skip to content
This repository has been archived by the owner on Jan 7, 2022. It is now read-only.

Add a warning about missing ordering key fields for data events #136

Merged
merged 2 commits into from
Mar 10, 2021

Conversation

a1exsh
Copy link
Contributor

@a1exsh a1exsh commented Mar 9, 2021

Internal ticket #552

Closes #134

, text " is used e.g. for analytics change data capture, i.e. keeping"
, text " transactional data in sync as source for analytics. The"
, text " information is recommended for (external) data change events"
, text "\u{00A0}-- see "
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

00A0 is a non-breaking space, in case someone's wondering ;)

@a1exsh
Copy link
Contributor Author

a1exsh commented Mar 9, 2021

👍

1 similar comment
@lmontrieux
Copy link
Contributor

👍

@a1exsh a1exsh merged commit 7759a2b into master Mar 10, 2021
@a1exsh a1exsh deleted the ordering-key-fields-warning branch March 10, 2021 10:51
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants